Skip to content

Changes to build.py #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 12 commits into
base: main
Choose a base branch
from
Open

Conversation

jmucchiello
Copy link

The important change is the in the build.py file. Including an empty localization.tsv can't hurt. In .gitignore, .vs/ is very important. The other changes, less so.

obj/
.vs/
Icon Sources/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels like a personal thing, not something that should be in the template

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The .vs/ thing kills me every time. I had to fork the mod-template. :)

# check dll has unique name
if DLL_NAME.lower() == "examplemod.dll":
print("Did you forget to rename the DLL in the project settings?")
exit(1);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is why pull requests aren't requests. Not demands. At least put something there.

@@ -0,0 +1 @@
Term Notes English
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if including a localization file is a good choice

  • People going through the tutorial could be confused by it, as the tutorial tells them to download a completely different file
  • I assume most people would use a tool like Google Sheets to edit their localization files instead of a code/text editor
  • Even if the above assumption is incorrect, it's easy enough to create manually thanks to the localization guide

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm old school. I edit the file in visual studio directly.

cleanup

frequency fix

Update README.md

Revert "Update README.md"

This reverts commit 35a1fda.

Revert "frequency fix"

This reverts commit 0290ac2.

Revert "cleanup"

This reverts commit 50815c1.

Revert "first commit"

This reverts commit 0e9481c.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants